From: Andrew Cooper Date: Mon, 10 Mar 2014 10:11:28 +0000 (+0100) Subject: kexec: identify which cpu the kexec image is being executed on X-Git-Tag: archive/raspbian/4.8.0-1+rpi1~1^2~5504 X-Git-Url: https://dgit.raspbian.org/%22http:/www.example.com/cgi/%22https:/%22bookmarks://%22Dat/%22http:/www.example.com/cgi/%22https:/%22bookmarks:/%22Dat?a=commitdiff_plain;h=4509ada6ba1f09cc8f4fa23e009e7e5a963b6086;p=xen.git kexec: identify which cpu the kexec image is being executed on A patch to this effect has been in XenServer for a little while, and has proved to be a useful debugging point for servers which have different behaviours depending when crashing on the non-bootstrap processor. Moving the printk() from kexec_panic() to one_cpu_only() means that it will only be printed for the cpu which wins the race along the kexec path. Signed-off-by: Andrew Cooper Acked-by: David Vrabel --- diff --git a/xen/common/kexec.c b/xen/common/kexec.c index 481b0c2fcf..23d964e1f9 100644 --- a/xen/common/kexec.c +++ b/xen/common/kexec.c @@ -265,6 +265,8 @@ static int noinline one_cpu_only(void) } set_bit(KEXEC_FLAG_IN_PROGRESS, &kexec_flags); + printk("Executing kexec image on cpu%u\n", cpu); + return 0; } @@ -340,8 +342,6 @@ void kexec_crash(void) if ( !test_bit(KEXEC_IMAGE_CRASH_BASE + pos, &kexec_flags) ) return; - printk("Executing crash image\n"); - kexecing = TRUE; if ( kexec_common_shutdown() != 0 )